--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Requests and Resources
Necom (Profile): (2025-09-05 09:03:50 (UTC))
So at first I thought the resource class was just like, more of an internal thing to make it easier to send files, but after reading the API reference (and talking to some people here) it seems to be an actual part of the protocol and handles coordinating with a peer, and checksumming. Also I think it uses requests, so is requesting a resource the same as accepting it? And if a resource is requested/accepted without having been advertised, will it still be sent? How can a program accept or reject a request for a resource?
Also, the way the API reference is written kind of makes it seem as though I’ve missed something. For example, the description under Link.request() simply says “Sends a request to the remote peer.”, without explaining what a request even is in the first place, implying it should already have been explained somewhere else. Is it true that these things are explained in some documentation that I’ve simply missed?
Also, (the answer to this is probably no, but) does anyone know when reticulum.network will be updated? It still says Reticulum is in beta...
Also, (the answer to this is probably no, but) does anyone know when reticulum.network will be updated? It still says Reticulum is in beta...
Doesn't look to be the case on my end.
I remember it being updated as soon as 1.0.0 came out. 🤔
Strange, could you show a screenshot of what that looks like? my lxmf is ee66ebab748238587ecdff6777b04260
Oh, you're talking about https://reticulum.network/start.html ?
Didn't see it before, sorry.
Make a PR or Issue here: https://github.com/markqvist/reticulum_website
Note that Mark has been away for a while and it won't be fixed until he's back.
Reticulum's documentation is not very good, you usually have to try to read the code...
Link.request() is an API to send requests on a link for a specific path(which will be hashed) with some (optional) extra data. the node can then respond with a resource or packet if the data is small enough. I don't know what happends when the path is unknown, it seems like the request is just ignored but that seems strange. this is what nomadnet uses btw.